home *** CD-ROM | disk | FTP | other *** search
- Path: america.com!not-for-mail
- From: "Holger Kruse" <kruse@america.com>
- Newsgroups: comp.sys.amiga.networking
- Subject: Re: Miami - a new TCP/IP stack for Internet access
- Date: Fri, 19 Apr 1996 07:27:35 -0500
- Organization: private Amiga site
- Message-ID: <kruse.53115951@america.com>
- References: <kruse.53115772@america.com> <4kn510$34v@news.uni-c.dk> <oj620lofcs8.fsf@hpsrk.fc.hp.com> <19960417.7D44D58.68FD@mojaveg.ridgecrest.ca.us>
- Reply-To: "kruse" <kruse@cs.ucf.edu>
- NNTP-Posting-Host: mco1-06.america.com
- X-NewsReader: IntuiNews 1.3a (7.9.95)
-
- In article <19960417.7D44D58.68FD@mojaveg.ridgecrest.ca.us>, Everett M. Greene
- <mojaveg@ridgecrest.ca.us> wrote:
-
- > My question: Why are the potential users of Miami being burdened
- > by MUI for a _portion_ of a program? As I understand it, Miami
- > needs MUI so that the configuration things can be done -- it isn't
- > part of the main application.
-
- This is not true. Both Miami (the protocol stack) and MiamiInit (the
- configuration program for starters) use MUI. Miami needs MUI for many
- things, including the dialer, configuration, and to view/change runtime
- settings.
-
- In case you are worried: MUI does definitely *not* slow down the
- protocol stack in any way. The device handler, protocol stack kernel,
- and MUI interface are located in three separate tasks, so none of the
- protocol stack routines, SLIP/PPP routines or clients/servers ever has
- to wait for a MUI layout to finish.
-
- --
- Holger Kruse kruse@cs.ucf.edu kruse@america.com
- http://www.america.com/~kruse/home.html
-
-